Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1124

reference: 681-tree-1
name: 1124
tree-preservation-order: undefined
681-tpo-1
uprn
address-text
point: POINT (-1.017661 50.880017)
geometry: MULTIPOLYGON (((-1.017618 50.880012,-1.017620 50.880021,-1.017626 50.880028,-1.017635 50.880034,-1.017647 50.880038,-1.017660 50.880040,-1.017673 50.880039,-1.017685 50.880035,-1.017695 50.880029,-1.017701 50.880021,-1.017703 50.880013,-1.017701 50.880005,-1.017696 50.879997,-1.017686 50.879991,-1.017674 50.879987,-1.017661 50.879986,-1.017648 50.879987,-1.017636 50.879991,-1.017627 50.879997,-1.017620 50.880004,-1.017618 50.880012)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL